Advanced loyalty applications for powered cards and devices

ABSTRACT

Advanced loyalty applications are provided to improve the functionality of cards and devices. For example, a user interface may be placed on a card (e.g., a physical button) or a telephonic device (e.g., a virtual button on a capacitive touch screen). Manual input provided to this user interface may, for example, cause a non-merchant product (e.g., insurance) to be purchased with a merchant purchase. The product can be paid for with debit, credit, gift card balance, or points. A code indicative of a user&#39;s desire to purchase the product may be communicated to a payment card reader (e.g., to a magnetic stripe reader via a magnetic stripe communications device). A display may be provided next to a button to allow a user to scroll, or toggle by pressing the button repeatedly, through different products (which may be merchant or non-merchant products).

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 13/944,455, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Jul. 17, 2013, which is a continuation of U.S. patent application Ser. No. 12/857,766, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Aug. 17, 2010, which claims the benefit of U.S. Provisional Patent Application No. 61/234,583, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed Aug. 17, 2009, each of which is hereby incorporated by reference herein in its their entirety.

BACKGROUND OF THE INVENTION

This invention relates to magnetic cards and devices and associated payment systems.

SUMMARY OF THE INVENTION

A card may include a dynamic magnetic communications device. Such a dynamic magnetic communications device may take the form of a magnetic encoder or a magnetic emulator. A magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium. A magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.

All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display). Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch-screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch. Accordingly, a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode.

A card may include a number of output devices to output dynamic information. For example, a card may include one or more RFIDs or IC chips to communicate to one or more RFID readers or IC chip readers, respectively. A card may include devices to receive information. For example, an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively. A device for receiving wireless information signals may be provided. A light sensing device or sound sensing device may be utilized to receive information wirelessly. A card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device). The central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device). A processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip. The processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card.

Advanced loyalty features are provided on cards and devices such as payment cards. Such cards and devices may, for example, allow a user to purchase a product not sold by a merchant when the card is used at that merchant. For example, a card or device may include a user interface able to receive manual input to indicate that a user desires to purchase a product not sold by a merchant (or a particular merchant product). Such a card or device may send information indicative of such a user desire during a payment transaction at the merchant. For example, information may be communicated in a discretionary data field of one or more tracks of magnetic stripe data (e.g., via a dynamic magnetic stripe communications device). As per another example, information may be communicated via RFID communications to an RFID reader or IC chip (e.g., EMV chip) communications to an IC chip reader. The value of such a product chosen by a user may be subtracted from a user's cash account, available line of credit, or available point balance. A display may be included to display information indicative of a user's selection (e.g., to purchase a non-merchant product) such that a user may enter this information into a data entry field of an online store. Such products may include, for example, damage insurance and/or theft insurance. Multiple user payment accounts may be linked. For example, if a user desires to pay for an additional product with points and that user's point balance does not have enough points to cover the purchase price of the product, then a user's credit or debit account may be utilized to pay for the entire price of the product or the outstanding balance needed to purchase the product. An LED may indicate a particular user selection (e.g., via different colors). A display may be provided next to a button such that a user can see information representative of the product being purchased. The product displayed may be toggled from a list of products by, for example, pressing a button additional times. A confirmation button may also be provided such that a user presses a button first to activate a display and display a product name and then presses the confirmation button to confirm. A card may include a default method of payment (e.g., credit, debit, gift balance, or points) associated with a particular button (e.g., a button for purchasing a particular product). Limitations with such a default (e.g., a minimum point balance needed to utilize a product purchase with points) may be communicated to a user at card issue (e.g., via physical mail, email, or posting on a user's account page of a card issuer's website).

A user interface is provided on a card or device that allows a user to indicate a desire to top-up a purchase to the nearest dollar (or other monetary unit) and use the excess to purchase additional points. For example, a user may press a button on a card associated with $5 such that every purchase is rounded up to the nearest $5. In doing so, any excess amount between the price of a purchase and the round-up interval may be utilized to purchase points at a particular conversion rate. The conversion rate to buy points in this manner may be different (e.g., more points may be purchased for a particular monetary unit) than the conversion rate to buy points outside of a purchase transaction.

All or a portion of the purchase price of merchant items may be paid for at the merchant using points. A card or device may include buttons associated with monetary amounts (e.g., $1, $5, and $10). A user may press a button associated with the desired amount of money a user desires to pay for an item with points. A user may select an amount greater than the purchase price and the difference may be added to a user's credit balance or debit account at a point-to-cash conversion rate. Such a conversion rate may be different (e.g., more points needed for a monetary unit) than if a user selects a monetary amount that only pays for a portion of a purchase.

A user may earn points for different point accounts by providing different manual input for the different point accounts. Different buttons may be provided on a card or device. One, more than one, or all point accounts may be point pools. A point pool may be connected to different accounts—such as different cards. Such different accounts may be owned by different users (e.g., a husband and a wife). Accordingly, for example, points may be shared between multiple users. For example, a card may have a vacation pool. Every member of the family may have a card linked to such a vacation pool. In order to redeem points in a pool, for example, a particular user (e.g., a father), multiple users (e.g., a father and a mother), or all users (e.g., all members of a family) may need to agree to redeem the points for a particular award (e.g., a free vacation). Such users can do so, for example, on each user's account webpage of a main account. Multiple people may also share the same account (e.g., a husband and a wife) such that two cards are issued with the same account number and share the same point account. A cardholder may elect to contribute some or all of the points earned with a purchase to the account of a beneficiary (e.g., a child).

A card is provided that includes a user interface for receiving manual input indicative of a user's desire to forego earning points with a purchase in order to obtain an entry into a lottery.

Alternatively, for example, an entry into a lottery may cost a particular number of points (e.g., over 1 point such as 50 points). Additionally, for example, an entry may only be able to be purchased while a user is purchasing an item or an entry may be able to be purchased at any time. Such a lottery may be held at least, for example, once a day, once a month, once a quarter, once every six months, or once a year. Multiple prizes and multiple winners may be included in each lottery. A winner of a lottery may win, for example, points (e.g., 1 million points), cash, and/or products. Non-point awards (e.g., plane tickets) may also be awarded in such a lottery.

A user interface may be provided on a card or button operable to receive manual input indicative of a user's desire to not earn points at a purchase from a merchant in order to obtain the ability to receive a particular point multiplier at the user's next purchase at that merchant so long as the purchase is transacted within a particular period of time (e.g., within a week or within a month). For example, a user may press a button on a card and associated information may be communicated in the discretionary data field of magnetic stripe data. Such a user may, for example, not earn any points with that purchase but may earn three times as many points with the next purchase at that merchant if the two purchases are made within a week of one another. The triple points may be, for example, limited to overlapping purchase value such that if the first purchase is $50 and the second purchase is $75 only $50 worth of purchase value obtains triple points. The remaining $25 of value may obtain no points or single points (regardless of the order of the $50 and $75 purchases). As per another example, the remaining $25 in value may receive double or triple points. Such a point bonus may be limited by a minimum purchase threshold for either a first or subsequent purchase (e.g., for qualifying purchases).

A card may be provided with an option (e.g., a manual user interface) for a user to select an opt-in marketing feature. Such a feature may send information to a merchant through, for example, magnetic stripe data communicated through a dynamic magnetic communications device. Such information may include, for example, demographic information or contact information (e.g., a user's email address). In turn, the merchant may fund a discount or additional points (e.g., a point multiplier such as double points) for the purchase. If a user has already used the opt-in feature at the merchant, the user may or may not be awarded the benefit associated with the user using the opt-in feature for the first time at a merchant. A merchant may send a user a communication (e.g., an email) as a result of receiving the user's email address in a communication to a payment card reader. The user may receive points from filling out such a survey.

Points may be utilized, for example, to purchase discounts for purchases. For example, a particular number of points may provide a 5%, 10%, 15%, or 20% discount on a purchase. A purchase limit for the discount may be provided (e.g., $100) or no purchase limit for the discount may be provided. If a limit is provided and the purchase is over the limit, the discount may only be applied to the limited amount (e.g., $100). Points may be utilized to purchase rebates (e.g., $5, $10, or $20) for a purchase. Such rebates or discounts may be, for example, open to all merchants or limited to qualifying purchases at participating merchants). Discounts and rebates may be processed by a card issuer by placing a credit on a credit statement having the value of the discount or rebate. In doing so, for example, rebates and discounts may be provided at any merchant without the knowledge of the merchant. Point levels required for purchase of a particular rebate or discount (or any other offering such as purchase insurance) may be communicated to a user via email, physical mail, or a user's account page on a card issuer's website. A product purchased with points via a button on a card may be, for example, an extended warranty associated with the products of a purchase as well as defect, damage, and/or theft protection. Other products purchased for points (or from other sources of payment) include, for example, product registration, expedited delivery, and ombudsman service.

Combinations of features may be provided on a card. For example, a card may be provided with a button associated with a feature that allows a user to earn a point multiplier at a second transaction within a period of time at a particular merchant. Another button may be provided on that card associated with a lottery feature. Yet another button may be provided on that card that allows a user to purchase a product at a purchase. Such a product may be associated with the purchase (e.g., purchase insurance for that product).

BRIEF DESCRIPTION OF THE DRAWINGS

The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:

FIG. 1 is an illustration of cards constructed in accordance with the principles of the present invention;

FIG. 2 is an illustration of a card constructed in accordance with the principles of the present invention;

FIG. 3 is an illustration of a card constructed in accordance with the principles of the present invention;

FIG. 4 is an illustration of a card constructed in accordance with the principles of the present invention; and

FIG. 5 is an illustration of a mobile device constructed in accordance with the principles of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows card 100 that may include, for example, a dynamic number that may be entirely, or partially, displayed via display 112. A dynamic number may include a permanent portion such as, for example, permanent portion 111. Permanent portion 111 may be printed as well as embossed or laser etched on card 100. Multiple displays may be provided on a card. For example, display 113 may be utilized to display a dynamic code such as a dynamic security code. Display 125 may also be provided to display logos, barcodes, as well as multiple lines of information. A display may be a bi-stable display or non bi-stable display. Permanent information 120 may also be included and may include information such as information specific to a user (e.g., a user's name or username) or information specific to a card (e.g., a card issue date and/or a card expiration date). Card 100 may include one or more buttons such as buttons 130-134. Such buttons may be mechanical buttons, capacitive buttons, or a combination or mechanical and capacitive buttons. Card 100 may include button 199. Button 199 may be used, for example, to communicate information through dynamic magnetic stripe communications device 101 indicative of a user's intent to purchase a particular product with a purchase for points.

Architecture 150 may be utilized with any card. Architecture 150 may include processor 120. Processor 120 may have on-board memory for storing information (e.g., application code). Any number of components may communicate to processor 120 and/or receive communications from processor 120. For example, one or more displays (e.g., display 140) may be coupled to processor 120. Persons skilled in the art will appreciate that components may be placed between particular components and processor 120. For example, a display driver circuit may be coupled between display 140 and processor 120. Memory 142 may be coupled to processor 120. Memory 142 may include data that is unique to a particular card. For example, memory 142 may store discretionary data codes associated with buttons of card 150. Such codes may be recognized by remote servers to effect particular actions. For example, a code may be stored on memory 142 that causes a non-merchant product to be purchased with points during a merchant transaction. Memory 142 may store loyalty information such as identifying information for a points account (e.g., a points account number) and associated information (e.g., a default preference on how points are earned during a purchase, such as 50% of a purchase's points is given to the user and 50% of a purchaser's points is used to purchase lottery entries for a lottery that has at least one award of a particular number of points).

Any number of reader communication devices may be included in architecture 150. For example, IC chip 152 may be included to communicate information to an IC chip reader. IC chip 152 may be, for example, an EMV chip. As per another example, RFID 151 may be included to communicate information to an RFID reader. A magnetic stripe communications device may also be included to communicate information to a magnetic stripe reader. Such a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader. Different electromagnetic signals may be communicated to a magnetic stripe reader to provide different tracks of data. For example, electromagnetic field generators 170, 180, and 185 may be included to communicate separate tracks of information to a magnetic stripe reader. Such electromagnetic field generators may include a coil wrapped around one or more materials (e.g., a soft-magnetic material and a non-magnetic material). Each electromagnetic field generator may communicate information serially to a receiver of a magnetic stripe reader for particular magnetic stripe track. Read-head detectors 171 and 172 may be utilized to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). This sensed information may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader. Accordingly, a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time. Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 152, and electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers). Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180, and 185.

FIG. 2 shows card 200 that includes button 211 associated with display 215, button 212 associated with display 216, and button 213 associated with display 217. Each button may be associated with a feature displayed in display 210. A user may press a button in order to communicate data representative of the feature through a magnetic stripe communications device or other communications device (e.g., RFID or IC chip). A light emitting diode (or other source of light) may be associated with each button to indicate to a user what feature was selected by a user. A user may be able to select multiple features such that multiple feature codes are communicated in tracks of magnetic stripe data communicated by a magnetic stripe communications device. Such codes may be provided in discretionary data fields. Such codes may be repeated on each track of communicated magnetic stripe data (e.g., repeated on tracks 1 and 2 or repeated on tracks 1, 2, and 3). In doing so, a user may associate multiple features to a purchase. A user may purchase a financial service by, for example, pressing button 211 for a purchase transaction. A user may press button 212 to enter into a lottery. The cost of the entry may be that no points are earned during the transaction. Button 213 may allow a user to earn multiple points if a purchase is made at the same merchant within a particular time period (e.g., over a day such as within a week) for a cost. The cost may be that a user does not earn any points with the initial purchase or earns a reduced amount of points (e.g., 50% point reduction). Persons skilled in the art will appreciate that one or more remote servers may manage a point balance as well as authorize and settle transactions.

The features associated with each card may be pre-determined by a user. For example, a user may select features to place on a card when ordering a card. Additionally, a user may go to a card issuer's website and select attributes of features. For example, a user may visit a card issuer's website and select the particular offering that is to be purchased whenever a user selects the feature associated with button 211 and displayed on display 215. Information associated with a button may be displayed via a display or permanently printed, embossed, or laser engraved on a card. Card 200 may include a light sensing device to receive information via light pulses from a display (e.g., a television, mobile phone, or laptop display). A user may select to change the features or attributes of features from a card issuer's websites and may reconfigure a card accordingly. Alternatively, a card may be provided with buttons and no descriptive information. A user may change the features or attributes of features associated with one or more buttons via a card issuer's website and remote processing may perform the associated processing as a result of on-card button selections. Different codes may be communicated depending on the feature or attributes of features on a card. Such codes may be changed via a wireless communications signal (e.g., a light-based communications signal). In doing so, processing may occur off-card at a remote server without the need to determine what feature a user associated with a code. Persons skilled in the art will appreciate that a card issuer may monitor the frequency and number of times that a user utilizes a particular feature. A card issuer may cross-sell new products based on this information. For example, suppose a user's card allows a user to purchase insurance for that purchase with a particular number of points. If the user utilizes this option at a particular frequency or a particular number of times, then the user may be sent an offer to purchase the product on a periodic subscription basis (e.g., monthly) instead of an individual purchase. The offer may be communicated, for example, via physical mail, email, or a card issuer's website. In doing so, a card issuer may convert cardholders to subscription-based products the cardholder has tested in a per-purchase environment. If a user purchases a subscription for a product that was associated with a button on a card, the card issuer may change the product associated with that button and notify the user of the change (e.g., via email or a card issuer's website). Persons skilled in the art will appreciate that various types of insurance may be provided. For example, insurance may be associated with a purchase such that if a merchant fails to deliver a product, the insurance covers the incident. Insurance may also be provided, for example, for damage to a product during shipping. Insurance may cover multiple types of incidents. A card issuer may add or modify the attributes of a feature. For example, a card issuer may modify or add products in a list of products associated with a buy product for points feature. The addition or modification may be communicated via light information pulses. Additionally, a user may be provided with a code to enter into buttons on a card where the code represents the modifications or additions. Additionally, the card may receive wireless communications signals (e.g., WiFi signals) associated with the modifications and additions). In this manner, a merchant may change the information on a display associated with a lottery feature to read “win 1M points” during a first period of time and “win Olympic tickets” during a second period of time.

A card issuer may provide a reward network of participating merchants. Accordingly, merchant specific promotions may be provided and paid for with points. For example, a particular merchant may allow for free overnight shipping for a particular number of points while another merchant may allow for an extended warranty for a particular number of points. All such promotions may be associated to a single button (or more than one button). Permanent indicia associated to the single button may generically describe all such merchant-specific promotions (e.g., “merchant promotion”). A different point conversion rate (e.g., a discounted lower point conversion rate) may be provided when items are purchased at a merchant inside of the rewards network versus merchants outside of the rewards network. Such products may be merchant products or non-merchant products. For example, a user may purchase any merchant items using points (e.g., any DVD at a Best Buy) but may receive different conversion rates for the points depending on whether the merchant is within a card issuer's reward network as well as the level of membership within that issuer's reward network. Merchants (e.g., merchants that are part of a particular rewards network) may be provided with devices that offer on-the-spot promotions. Such devices may emit light pulses or other communication signals that are received and stored on a card or other device. A card may prompt a user to interact with a card (e.g., press a button) to confirm acceptance and desire to use a communicated promotion. A promotion may be paper based, but may interact with payment process that includes a card or other device. For example, a user may pick up a coupon that states “give this coupon to a friend and if that friend makes a purchase within 10 days, you will get double points.” The cashier may then scan the barcode of the coupon and a user may press a MERCHANT OFFER button on a card. The merchant system may similarly send the coupon code to a remote system. An associated code may be communicated with payment information (e.g., magnetic stripe data) to the remote system. The remote system may then associate the purchase with the coupon code. Upon a friend redeeming the coupon, the user associated with the original payment information may be provided with additional points (e.g., double points). As per another example, a merchant may pre-register with a card issuer the merchant's promotion. The promotion may be, for example, a cross-merchant promotion where a user that purchases an item at one merchant may receive double points and a 10% discount if a paper coupon is used within a particular number of days at a different merchant. To qualify, a user may be required to press a MERCHANT OFFER button. A card issuer may then retrieve the promotion for the merchant from a database to learn that the user has opted in for the cross-merchant promotion. Accordingly, the card issuer's processing system may periodically check during the promotional window (or at the end of the promotion) whether the user has made a purchase at the second merchant to receive the double points. The coupon may be utilized at the second merchant to receive the 10% discount. Alternatively, for example, the coupon may also be needed to obtain the double points in addition to the 10%.

FIG. 3 shows card 300 that may include dynamic magnetic stripe communications device 310, buttons 311-315, permanent information 320, display 350, data receiving device 370, and buttons 331-333. Button 331 may be associated with a first line of displayed information on display 350. Button 332 may be associated with a second line of displayed information on display 350. Button 333 may be associated with a third line of displayed information on display 350. Persons skilled in the art will appreciate that buttons 331-333 may actually be virtual buttons on display 350 and display 350 may be a capacitive touch screen. Data receiving device 370 may be a light or sound sensor for receiving information through received light or sound.

FIG. 4 shows card 400 that may include signature line 410 and display 420. Persons skilled in the art will appreciate that card 300 of FIG. 3 may depict the obverse side of a card and card 400 of FIG. 4 may depict the reverse side of a card. Individual components of card 300 of FIG. 3 or card 400 of FIG. 4 may be provided on either side of a card or both sides of a card. More than one instance of a component may be provided on any side of a card (e.g., the same side as a component or a different side as a component). Persons skilled in the art will appreciate that a user may communicate feature codes representative of a user's on-card selection via codes that may be displayed visually and entered into a webpage as part of an online payment. A display may display not only a code for an online payment, but also indicia representative of the feature. In doing so, the user can confirm that the right feature was selected. Persons skilled in the art will appreciate that different codes for the same feature may be displayed and communicated via a dynamic magnetic communications device. In doing so, the security of the card may be increased. Additionally, the same or different codes may be communicated on different tracks of data to represent the selection of a particular feature.

FIG. 5 shows mobile device 500, which may be a mobile telephonic device. Device 500 may include one or more physical buttons (e.g., button 540). Device 500 may include one or more display screens 510. Such a display screen may be touch sensitive such that virtual buttons (e.g., button 530 may be provided) on virtual card 520. Virtual card 520 may appear similar to a physical card described herein. A user may select different virtual cards by, for example, swiping his/her finger across a touch-sensitive display to scroll to the next virtual card. Mobile phone 502 may include a communications device operable to communicate data to a card reader. For example, mobile phone 502 may include an RFID antenna to communicate to an RFID reader, a pop-out IC chip panel operable to be fed into an IC chip reader, or a magnetic communications device having a magnetic emulator operable to communicate magnetic stripe data wirelessly to a read-head of a magnetic stripe reader.

Persons skilled in the art will also appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways than those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow. 

What is claimed is:
 1. A method, comprising; receiving, by a server, transaction data as part of a first transaction with a first transactional entity, the transaction data including first information associated with the first transaction and second information associated with a second transaction including a second transactional entity different from the first transactional entity.
 2. The method of claim 1, further comprising: causing, by the server, a purchase using cash from a debit account based on the second information.
 3. The method of claim 1, further comprising: causing, by the server, a purchase using points based on the second information.
 4. The method of claim 1, further comprising: causing, by the server, a purchase using credit from a credit account based on the second information.
 5. The method of claim 1, wherein the second information is indicative of a product not sold by the first transactional entity.
 6. The method of claim 1, further comprising: causing, by the server, a purchase of insurance based on the second information.
 7. The method of claim 1, further comprising: parsing data in a discretionary data field of magnetic stripe data to determine the second information, wherein the transaction data includes the magnetic stripe data.
 8. The method of claim 1, further comprising: authorizing, by the server, a first purchase based on payment data; and causing, by the server, the second transaction based on information indicative of a product not sold by the first transactional entity, wherein the first transaction includes the first purchase, the first information includes the payment data, and the second information includes the information indicative of a product not sold by the first transactional entity.
 9. The method of claim 1, further comprising: authorizing, by the server, a first purchase based on payment data; and causing, by the server, a second purchase based on information indicative of a purchase using cash from a debit account, wherein the first transaction includes the first purchase, the second transaction includes the second purchase, the first information includes the payment data, and the second information includes the information indicative of a purchase using cash from a debit account.
 10. The method of claim 1, further comprising: authorizing, by the server, a first purchase based on payment data; and causing, by the server, a second purchase based on information indicative of purchasing points, wherein the first transaction includes the first purchase, the second transaction includes the second purchase, the first information includes the payment data, and the second information includes the information indicative of purchasing points.
 11. The method of claim 1, further comprising: authorizing, by the server, a first purchase using points; and causing, by the server, a second purchase based on information indicative of purchasing points, wherein the first transaction includes the first purchase, the second transaction includes the second purchase, the first information includes the payment data, and the second information includes the information indicative of purchasing points.
 12. The method of claim 1, wherein the second information is indicative of a first product not sold by the transactional entity, and the first product is associated with a second product, the second product sold by the transactional entity.
 13. The method of claim 1, wherein the first transaction is a purchase of a first product, the second transaction is a purchase of a second product not sold by the transactional entity, the second information is indicative of the second product, and the second product is associated with the first product.
 14. The method of claim 1, wherein the first transaction is a purchase of a first product, the second information is indicative of a purchase of a second product not sold by the transactional entity, the second product associated with the first product, and the second product is at least one of an extended warranty, defect protection, damage protection, theft protection, product registration, insurance, expedited delivery, and ombudsman service. 